language en

Linked.Archi EA on a Page Ontology

Release: 2020-07-27

Modified on: 2026-05-03
This version:
https://meta.linked.archi/eaonapage/onto/0.1.0#
Revision:
0.1.0
Issued on:
2020-07-27
Authors:
Kalin Maldzhanski
Publisher:
Linked.Archi
Source:
https://eaonapage.com/
https://kotusev.com/Enterprise%20Architecture%20-%20Forget%20Systems%20Thinking,%20Improve%20Communication.pdf
https://kotusev.com/Enterprise%20Architecture%20Artifacts%20-%20Facts%20and%20Decisions.pdf
https://kotusev.com/The%20Process%20View%20of%20Enterprise%20Architecture%20Practice.pdf
https://meta.linked.archi/eaonapage/onto#Kotusev2021
https://meta.linked.archi/eaonapage/onto#Kotusev2024
https://www.bcs.org/media/3787/csvlod.pdf
https://www.kotusev.com/Yet%20Another%20Taxonomy%20for%20Enterprise%20Architecture%20Artifacts.pdf
See also:
http://kotusev.com/
https://eaonapage.com/
https://www.bcs.org/articles-opinion-and-research/enterprise-architecture-on-a-single-page
https://www.bcs.org/articles-opinion-and-research/enterprise-architecture-practice-on-a-single-page
Download serialization:
JSON-LD RDF/XML N-Triples TTL
License:
http://creativecommons.org/licenses/by/4.0/
Visualization:
Visualize with WebVowl
Cite as:
Kalin Maldzhanski. Linked.Archi EA on a Page Ontology. Revision: 0.1.0. Retrieved from: https://meta.linked.archi/eaonapage/onto/0.1.0#
Provenance of this page
draft

Abstract

OWL ontology for the EA on a Page framework — six CSVLOD artifact type classes with inter-type relationships, classification properties, processes, process phases, governance model, participants, and maturity stages.

Linked.Archi EA on a Page Ontology: Overview back to ToC

This ontology has the following classes and properties.

Classes

Object Properties

Data Properties

Annotation Properties

Named Individuals

Linked.Archi EA on a Page Ontology: Description back to ToC

Ontology for the Enterprise Architecture on a Page framework by Svyatoslav Kotusev. Defines the six CSVLOD artifact types as OWL classes (Consideration, Standard, Vision, Landscape, Outline, Design) with inter-type relationship properties describing how artifact types influence each other within an EA practice. Also defines EA processes (Strategic Planning, Initiative Delivery, Technology Optimization), process phases, governance activities, participants, governance bodies and tiers, and maturity stages. Finer-grained classification of the 24 specific artifact types is handled via eaop:classifiedByType pointing to SKOS concepts in the companion taxonomy (eaonapage-tax.ttl). Based on peer-reviewed research across 27+ organizations, this framework describes how EA practices actually work rather than prescribing how they should work. This is not an official IASA document.

Cross-reference for Linked.Archi EA on a Page Ontology classes, object properties and data properties back to ToC

This section provides details for each class and property defined by Linked.Archi EA on a Page Ontology.

Classes

Amendmentc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Amendment

A governance activity where an approved architecture artifact is modified to reflect changed requirements or new constraints.
has super-classes
Governance Activity c

Approvalc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Approval

A governance decision to approve an architecture artifact or initiative to proceed.
has super-classes
Governance Activity c

Architecture Reviewc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#ArchitectureReview

A governance activity where architecture artifacts are reviewed against standards, principles, and strategic direction.
has super-classes
Governance Activity c

Architecture Tierc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#ArchitectureTier

A level in the architecture governance hierarchy. EA on a Page describes one-tier, two-tier, and three-tier governance models depending on organizational size and complexity. Each tier has its own governance bodies, governed artifact types, and decision authority.
is in domain of
tier level dp
is in range of
governs tier op

Artifact Typec back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#ArtifactType

A specific artifact type from the CSVLOD taxonomy — classification slot for architecture work products within an EA practice. Instances are the 24 specific artifact types defined in the taxonomy (e.g., Principles, Technology Reference Models, Business Capability Models, Landscape Diagrams, Solution Overviews, Solution Designs). Same role as zach:ZachmanCell.
is in range of
classified by type op

Business Leaderc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#BusinessLeader

has super-classes
EA Practice Participant c
is also defined as
named individual

Considerationc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Consideration

Abstract high-level guidelines or imperatives defining an entire organization. Considerations are overarching conceptual rules important for business executives while also having significant technology-related ramifications. They represent planning decisions established collaboratively by business executives and architects. Due to their implicit duality, Considerations convey one value-related meaning to business executives but another infrastructure-related meaning to architects. Considerations are permanent, very long-lived, established once and then periodically updated. After being agreed upon, they provide a common basis for all further discussions and influence all other artifact types.
Example
Architecture principles defining process standardization and data centralization policies, business continuity requirements.
is in domain of
influence creation op, influence design structure op, influence evolution op, influence outline structure op, influence selection op, influence structure op

Designc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Design

Detailed technical descriptions of separate IT systems actionable for their implementers. Designs provide IT specialists with precise technology- specific information required to deliver the project but are largely irrelevant to business executives. They represent technical planning decisions developed collectively by architects and IT project teams based on corresponding Outlines. Due to their duality, Designs convey one meaning to architects (standards compliance, strategic alignment) and another to project teams (implementation plan). Designs are temporary and limited in their active lifespan to the duration of respective projects.
Example
Solution designs describing in detail application, data, technology and security layers of the IT system.
is in range of
guide structure op, influence design structure op, provide basis op, provide environment for design op, provide guidelines for design op

EA Maturity Stagec back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#MaturityStage

A stage in the maturity of an EA practice, characterized by the processes established, artifacts mastered, governance arrangements in place, and benefits realized. EA on a Page defines four stages from Stage Zero (no architecture) to Stage Three (true enterprise architecture).
is in domain of
has governance arrangement op, maturity benefit dp, maturity challenge dp, maturity stage process op

EA Practice Participantc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#EAParticipant

A stakeholder who participates in EA practice processes.
has super-classes
stakeholder c
has sub-classes
Business Leader c, Enterprise Architect c, IT Leader c, Solution Architect c
is in range of
process participant op

EA Processc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#EAProcess

A core process in an EA practice as defined by the EA on a Page framework. EA practices consist of three distinct but interrelated processes that revolve around the six types of EA artifacts.
has super-classes
architecture process c
has sub-classes
Initiative Delivery c, Strategic Planning c, Technology Optimization c
is in domain of
has phase op, process participant op
is in range of
maturity stage process op, used in process op

EA Process Phasec back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#EAProcessPhase

A phase or sub-activity within one of the three core EA processes. Phases represent the lifecycle stages that initiatives pass through within each process.
has super-classes
architecture process c
has sub-classes
Governance Activity c, Initiation c, Realization c, Strategic Planning Cycle c
is in range of
has phase op

Enterprise Architectc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#EnterpriseArchitect

has super-classes
EA Practice Participant c
is also defined as
named individual

Escalationc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Escalation

A governance activity where a decision or conflict is escalated to a higher-tier governance body for resolution.
has super-classes
Governance Activity c

Exemptionc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Exemption

A governance decision to grant a temporary deviation from established standards or principles for a specific initiative.
has super-classes
Governance Activity c

Governance Activityc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#GovernanceActivity

An activity within EA governance processes, including architecture reviews, approvals, amendments, exemptions, and escalations.
has super-classes
EA Process Phase c
has sub-classes
Amendment c, Approval c, Architecture Review c, Escalation c, Exemption c

Governance Arrangementc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#GovernanceArrangement

A configuration of governance bodies, tiers, decision rights, escalation paths, and governed artifact categories that defines how architecture governance operates in an organization. Different maturity stages and organizational sizes lead to different governance arrangements.
is in range of
has governance arrangement op

Governance Bodyc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#GovernanceBody

An organizational body that governs architecture decisions and artifacts. Governance bodies review, approve, or reject architecture artifacts and decisions at various levels of the organization. Examples include architecture review boards, steering committees, and technology councils.
has super-classes
stakeholder c
is in domain of
escalates to op, governs tier op
is in range of
escalates to op, governed by op

Initiationc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Initiation

has super-classes
EA Process Phase c
is also defined as
named individual

Initiative Deliveryc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#InitiativeDelivery

has super-classes
EA Process c
is also defined as
named individual

IT Leaderc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#ITLeader

has super-classes
EA Practice Participant c
is also defined as
named individual

Landscapec back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Landscape

Formal models or diagrams describing the IT landscape from the technology perspective at various scopes and levels of granularity. Landscapes are important for architects but virtually useless to business executives. They represent documented facts and may be developed and maintained by individual architects alone. Unlike Visions which focus on the future, Landscapes aim to capture the current as-is state. They provide a baseline or inventory of the existing IT infrastructure. Landscapes are permanent, long-lived, and evolve reactively together with the organization — updated after changes in the landscape occur.
Example
Landscape diagrams depicting main applications, systems, databases and connections between them.
is in domain of
provide environment op, provide environment for design op, provide environment for outline op
is in range of
eventually shape op, guide evolution op, influence evolution op

Outlinec back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Outline

High-level descriptions of separate IT projects understandable to business executives. Outlines provide decision-makers with relevant summary information about a proposed new IT system but do not contain sufficient technical details to actually implement it. They represent planning decisions created collaboratively by architects and business executives based on basic requirements. Outlines are often initiated from Visions and are consistent with Considerations. Due to their explicit duality, Outlines convey one meaning to business executives (value, timelines, costs) and another to architects (what needs to be delivered). Outlines are temporary and short-lived — created at early stages of projects to support decision-making, then discarded after projects are initiated or rejected.
Example
Solution overviews describing the essence of the proposed IT solution, its overall impact, estimated cost, time and risks.
is in domain of
provide basis op
is in range of
influence outline structure op, initiate new op, provide environment for outline op, provide guidelines for outline op

Realizationc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Realization

has super-classes
EA Process Phase c
is also defined as
named individual

Solution Architectc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#SolutionArchitect

has super-classes
EA Practice Participant c
is also defined as
named individual

Standardc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Standard

Highly specialized low-level technical guidelines prescribing how the IT landscape should be organized and built. Standards are critically important for architects but largely irrelevant to business executives. They represent technical planning decisions established collectively by architects based on their understanding of the best interests of business executives. Unlike dual Considerations, Standards are virtually invisible to business executives since they reflect technology-specific rules. Standards are permanent and relatively stable, updated periodically with new technologies or better approaches. After being established, Standards influence the designs of all individual IT systems and the overall structure of the IT landscape.
Example
Technology standards prescribing application platforms, database management systems, proven integration patterns.
is in domain of
eventually shape op, provide guidelines op, provide guidelines for design op, provide guidelines for outline op
is in range of
guide selection op, influence selection op

Strategic Planningc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#StrategicPlanning

has super-classes
EA Process c
is also defined as
named individual

Strategic Planning Cyclec back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#StrategicPlanningCycle

has super-classes
EA Process Phase c
is also defined as
named individual

Technology Optimizationc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#TechnologyOptimization

has super-classes
EA Process c
is also defined as
named individual

Visionc back to ToC or Class ToC

IRI: https://meta.linked.archi/eaonapage/onto#Vision

Abstract, often one-page diagrams providing high-level views of an entire organization, typically describing the strategic development plan 3-5 years ahead. The long-term strategy reflected in Visions is critical for business executives while also having direct implications for the IT landscape. Visions represent planning decisions developed collaboratively by business executives and architects. Due to their implicit duality, Visions convey one meaning to business executives (strategic priorities) and another to architects (IT investment direction). Visions are permanent but evolving, continuously updated according to the latest strategic changes. After being developed, they provide a basis for directing future investments and prioritizing proposed projects.
Example
Business capability maps showing which capabilities should be uplifted, target state architectures, strategic roadmaps.
is in domain of
guide evolution op, guide selection op, guide structure op, initiate new op
is in range of
influence creation op

Object Properties

artifact focusop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#artifactFocus

Whether an artifact is primarily business-focused or IT-focused. Values are SKOS concepts from the EA on a Page taxonomy.
Example
ex:MyArtifact eaop:artifactFocus eaoptax:ITFocused .

artifact lifecycleop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#artifactLifecycle

The temporal lifecycle of an artifact: permanent, long-lived, or short-lived. Values are SKOS concepts from the EA on a Page taxonomy.
Example
ex:MyArtifact eaop:artifactLifecycle eaoptax:Permanent .

artifact natureop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#artifactNature

The nature of what an artifact describes: rules, structures, or changes. Based on Kotusev's three-way classification. Values are SKOS concepts from the EA on a Page taxonomy.
Example
ex:MyArtifact eaop:artifactNature eaoptax:Rules .

artifact scopeop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#artifactScope

The organizational scope of an artifact: organization-wide, initiative-scoped, or project-scoped. Values are SKOS concepts from the EA on a Page taxonomy.
Example
ex:MyArtifact eaop:artifactScope eaoptax:OrganizationWide .

classified by typeop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#classifiedByType

Links an architecture work product to its specific artifact type in the CSVLOD taxonomy. The target is a skos:Concept from the EA on a Page taxonomy (eaonapage-tax.ttl) — one of the 24 specific artifact types. Same design pattern as zach:classifiedByCell.
has range
Artifact Type c

escalates toop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#escalatesTo

Links a governance body to the higher-tier body it escalates decisions to.
has domain
Governance Body c
has range
Governance Body c

eventually shapeop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#eventuallyShape

Standards eventually shape Landscapes — by guiding individual project decisions, Standards determine the structure of the IT landscape that results from those projects.
has domain
Standard c
has range
Landscape c

governed byop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#governedBy

Links an architecture work product to the governance body responsible for its review and approval.
has range
Governance Body c

governs tierop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#governsTier

Links a governance body to the architecture tier it operates at.
has domain
Governance Body c
has range
Architecture Tier c

guide evolutionop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#guideEvolution

Visions guide the evolution of Landscapes.
has domain
Vision c
has range
Landscape c

guide selectionop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#guideSelection

Visions guide the selection of Standards.
has domain
Vision c
has range
Standard c

guide structureop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#guideStructure

Visions guide the structure of Designs.
has domain
Vision c
has range
Design c

has governance arrangementop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#hasGovernanceArrangement

Links a maturity stage to the governance arrangement typically observed at that stage.
has domain
EA Maturity Stage c
has range
Governance Arrangement c

has phaseop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#hasPhase

Links an EA process to one of its constituent phases or sub-activities.
has domain
EA Process c
has range
EA Process Phase c

influence creationop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#influenceCreation

Considerations influence the creation of Visions.
has domain
Consideration c
has range
Vision c

influence design structureop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#influenceDesignStructure

Considerations influence the structure of Designs.
has super-properties
influence structure op
has domain
Consideration c
has range
Design c

influence evolutionop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#influenceEvolution

Considerations influence the evolution of Landscapes.
has domain
Consideration c
has range
Landscape c

influence outline structureop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#influenceOutlineStructure

Considerations influence the structure of Outlines.
has super-properties
influence structure op
has domain
Consideration c
has range
Outline c

influence selectionop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#influenceSelection

Considerations influence the selection of Standards.
has domain
Consideration c
has range
Standard c

influence structureop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#influenceStructure

Considerations influence the structure of Outlines and Designs.
has sub-properties
influence design structure op, influence outline structure op
has domain
Consideration c

initiate newop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#initiateNew

Visions initiate the creation of new Outlines for specific IT projects required to achieve the desired future.
has domain
Vision c
has range
Outline c

maturity stage processop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#maturityStageProcess

Links a maturity stage to the EA processes typically established at that stage.
has domain
EA Maturity Stage c
has range
EA Process c

process participantop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#processParticipant

Links an EA process to a participant role.
has domain
EA Process c
has range
EA Practice Participant c

provide basisop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#provideBasis

Outlines provide the initial basis for developing more detailed Designs.
has domain
Outline c
has range
Design c

provide environmentop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#provideEnvironment

Landscapes provide the environment for all new IT systems described in Outlines and Designs.
has sub-properties
provide environment for design op, provide environment for outline op
has domain
Landscape c

provide environment for designop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#provideEnvironmentForDesign

Landscapes provide the environment for Designs.
has super-properties
provide environment op
has domain
Landscape c
has range
Design c

provide environment for outlineop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#provideEnvironmentForOutline

Landscapes provide the environment for Outlines.
has super-properties
provide environment op
has domain
Landscape c
has range
Outline c

provide guidelinesop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#provideGuidelines

Standards provide implementation-specific guidelines for developing Outlines and Designs.
has sub-properties
provide guidelines for design op, provide guidelines for outline op
has domain
Standard c

provide guidelines for designop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#provideGuidelinesForDesign

Standards provide guidelines for developing Designs.
has super-properties
provide guidelines op
has domain
Standard c
has range
Design c

provide guidelines for outlineop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#provideGuidelinesForOutline

Standards provide guidelines for developing Outlines.
has super-properties
provide guidelines op
has domain
Standard c
has range
Outline c

usage frequencyop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#usageFrequency

How commonly the artifact type is used across organizations: essential, common, or uncommon. A type-level classification property. Values are SKOS concepts from the EA on a Page taxonomy.
Example
eaoptax:Principles eaop:usageFrequency eaoptax:Essential .

used in processop back to ToC or Object Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#usedInProcess

Links an architecture work product to the EA process it is used in.
has range
EA Process c

Data Properties

maturity benefitdp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#maturityBenefit

A benefit typically realized at a given maturity stage, based on empirical observation across organizations.
has domain
EA Maturity Stage c
has range
string

maturity challengedp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#maturityChallenge

A challenge typically faced at a given maturity stage, based on empirical observation across organizations.
has domain
EA Maturity Stage c
has range
string

tier leveldp back to ToC or Data Property ToC

IRI: https://meta.linked.archi/eaonapage/onto#tierLevel

The numeric level of an architecture tier in the governance hierarchy: 1 (enterprise), 2 (domain/segment), 3 (solution/project).
has domain
Architecture Tier c
has range
integer

Annotation Properties

abstractap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/abstract

createdap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/created

creatorap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/creator

dateap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/date

definitionap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#definition

descriptionap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/description

editionap back to ToC or Annotation Property ToC

IRI: http://purl.org/ontology/bibo/edition

exampleap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#example

isbn13ap back to ToC or Annotation Property ToC

IRI: http://purl.org/ontology/bibo/isbn13

issuedap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/issued

licenseap back to ToC or Annotation Property ToC

IRI: http://creativecommons.org/ns#license

modifiedap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/modified

pref labelap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#prefLabel

preferred namespace prefixap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespacePrefix

preferred namespace uriap back to ToC or Annotation Property ToC

IRI: http://purl.org/vocab/vann/preferredNamespaceUri

publisherap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/publisher

scope noteap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/2004/02/skos/core#scopeNote

sourceap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/source

statusap back to ToC or Annotation Property ToC

IRI: http://purl.org/ontology/bibo/status

titleap back to ToC or Annotation Property ToC

IRI: http://purl.org/dc/terms/title

was derived fromap back to ToC or Annotation Property ToC

IRI: http://www.w3.org/ns/prov#wasDerivedFrom

Named Individuals

Initiative Deliveryni back to ToC or Named Individual ToC

IRI: https://meta.linked.archi/eaonapage/onto#InitiativeDelivery

has facts
has phase op Initiation
has phase op Realization
process participant op Enterprise Architect
process participant op Solution Architect
is also defined as
class

kotusev2021ni back to ToC or Named Individual ToC

IRI: https://meta.linked.archi/eaonapage/onto#Kotusev2021

belongs to
book c
entity c

kotusev2024ni back to ToC or Named Individual ToC

IRI: https://meta.linked.archi/eaonapage/onto#Kotusev2024

belongs to
book c
entity c

Strategic Planningni back to ToC or Named Individual ToC

IRI: https://meta.linked.archi/eaonapage/onto#StrategicPlanning

has facts
has phase op Strategic Planning Cycle
process participant op Business Leader
process participant op Enterprise Architect
process participant op IT Leader
is also defined as
class

Technology Optimizationni back to ToC or Named Individual ToC

IRI: https://meta.linked.archi/eaonapage/onto#TechnologyOptimization

has facts
process participant op Enterprise Architect
process participant op IT Leader
is also defined as
class

Legend back to ToC

c: Classes
op: Object Properties
dp: Data Properties
ni: Named Individuals

Acknowledgments back to ToC

The authors would like to thank Silvio Peroni for developing LODE, a Live OWL Documentation Environment, which is used for representing the Cross Referencing Section of this document and Daniel Garijo for developing Widoco, the program used to create the template used in this documentation.